Individual mobile devices as edge network

ABSTRACT

A system includes a participating device, an input-output interface, and a processor coupled to the input-output interface wherein the processor is further coupled to a memory, the memory having stored thereon executable instructions that when executed by the processor cause the processor to effectuate operations including authenticating the participating device as an edge device on a network, allocating a resource on the participating device to be used for serving a user device operating on the network, receiving a request for service from the user device, and causing the participating device to provide a service to the user devices using the resource from the participating device.

TECHNICAL FIELD

This disclosure is directed to a system and method for edge computing ina network, and, more specifically, to utilizing processing capabilitiesin mobile devices to expand network services in an edge computingenvironment.

BACKGROUND

Edge computing is a distributed computing system in which processing anddata storage is provided closer to the location where the processing anddata storage is used or needed. As such, the computation may beperformed on distributed device nodes. Edge computing pushesapplications, data and computing power away from centralized points tolocations closer to the user. Edge computing is useful, for example, inmany internet of things applications.

As the concept of edge computing continues to grow, telecom networkssuch as 4G LTE and especially 5G networks need to continue to adopt suchedge computing concepts. Doing so will enable additional connectivityand more efficient data processing. With the further advancement ofsmart phones and other smart mobile devices, the telecom networks nowhave significant and ever-increasing processing resources at the edge oftheir networks. As such, there is a need to securely and seamlessly pushthe edge of the network into individual mobile devices to form dynamicsecure network access which is no longer constrained by geographiclimits.

SUMMARY

The present disclosure is directed to a system including a participatingdevice, an input-output interface, a processor coupled to theinput-output interface wherein the processor is further coupled to amemory, the memory having stored thereon executable instructions thatwhen executed by the processor cause the processor to effectuateoperations including authenticating the participating device as an edgedevice on a network, allocating a resource on the participating deviceto be used for serving a user device operating on the network, receivinga request for service from the user device and Causing the participatingdevice to provide the service to the user devices using the resource.The operations may further include allocating a resource on a secondparticipating device and causing the service to be transitioned from theparticipating device to the second participating device. Theparticipating device may provide an identification of the last taskbeing executed by the user mobile device to the second participatingdevice. The first participating device and the second participatingdevice are in communication with a common network edge device. In anaspect, the user device may be outside of a coverage area of the networkand the user device connects to the network through the participatingdevice. The user device may be authenticated on the network through aregistration process on backend server in the network.

In an aspect, a second resource is allocated on the participating deviceand wherein the operations further include receiving a request for asecond service from a second user device and causing the participatingdevice to provide the second service to the second user device using thesecond resource and wherein the first resource and the second resourceare securely isolated from each other on the participating device. Theparticipating device may have a usage profile wherein the user profileincludes resources available to be allocated as an edge device. Theresource may be one of a computation, storage, or routing resource.

The disclosure is also directed to a method including registering as aparticipating device on a network, allocating a portion of availableresources on the participating device to be shared with a user device,and establishing a first communication with the user device using theportion of available resources. The method may further include handingoff the first communication to an edge network device or a secondparticipating device. In an aspect, the method may further includeallocating a second portion of available resources to be shared with asecond user device and establishing a second communication with thesecond user device. In an aspect, the method may further includeestablishing a second communication with an edge network device andwherein the user device is authenticated through a back-end server andthe first communication is initiated by the edge network device whereinthe establishing step is initiated by the user device operating outsideof a coverage area of the network. The participating device may receivebilling credits for sharing resources used in the first communication

The disclosure is also directed to a mobile device including aprocessor, a user device portion configured to operate on a network, aparticipating device portion configured to operate as an edge device onthe network wherein the participating device portion and the user deviceportion are isolated from each other in secure containers and anapplication configured to execute on the mobile device, the applicationhaving stored executable instructions in a memory that when executed bythe processor cause the processor to effectuate operations includingregistering on the network as a participating device, receiving a firstcommunication from a first edge device on the network, the firstcommunication containing a request for resources to be used by a seconduser device, and establishing a second communication with the seconduser device and wherein the second communication includes providingoperating resources from the participating device portion to be used bythe second user device. In an aspect, the participating device portionis divided into two or more secure containers, each of the securecontainers having resources to be allocated to the second user deviceand a third user device

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the herein described telecommunications network and systemsand methods for controlling vehicular traffic are described more fullywith reference to the accompanying drawings, which provide examples. Inthe following description, for purposes of explanation, numerousspecific details are set forth in order to provide an understanding ofthe variations in implementing the disclosed technology. However, theinstant disclosure may take many different forms and should not beconstrued as limited to the examples set forth herein. Where practical,like numbers refer to like elements throughout.

FIG. 1a is a block diagram of an exemplary operating environment inaccordance with the present disclosure.

FIG. 1b is a functional block diagram of an exemplary application thatmay be developed for use in the participating network device shown inFIG. 1 a.

FIG. 2a is a functional block diagram of an exemplary operatingenvironment illustrating multiple use cases of the present disclosure.

FIG. 2b is a flowchart of an exemplary method of connecting and usingparticipating mobile devices as edge network devices.

FIG. 2c is a flowchart illustrating an exemplary use case for a usermobile device connecting to a core network when otherwise out of rangeof the core network.

FIG. 2d is a flowchart illustrating an exemplary use case for a usermobile device connecting to a peer participating mobile device forservices.

FIG. 3 is a schematic of an exemplary network device.

FIG. 4 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate.

FIG. 5 depicts an exemplary communication system that provide wirelesstelecommunication services over wireless communication networks withwhich edge computing node may communicate.

FIG. 6 is a diagram of an exemplary telecommunications system in whichthe disclosed methods and processes may be implemented with which edgecomputing node may communicate.

FIG. 7 is an example system diagram of a radio access network and a corenetwork with which edge computing node may communicate.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a general packet radioservice (GPRS) network, with which edge computing node may communicate.

FIG. 9 illustrates an exemplary architecture of a GPRS network withwhich edge computing node may communicate.

FIG. 10 is a block diagram of an exemplary public land mobile network(PLMN) with which edge computing node may communicate.

DETAILED DESCRIPTION

System Overview. Cellular communications systems that take advantage ofedge computing techniques have pushed functionality typically located inthe core network to the network edge. The system of the presentdisclosure pushes the network edge further to smartphones or othermobile devices connected to the network. The system utilizes acombination of fixed and mobile assets to expand network edgecapabilities for time-sensitive and/or resource-intensivecommunications. The fixed assets may include network edge equipment,including processors and databases, connected to a wireless network. Themobile assets may include a plurality of user mobile devices which maybe smartphones.

In an aspect, the disclosure includes a mechanism to push the edgenetwork into individual mobile devices. Owners of mobile devices thatelect to participate in the expanded edge concept may share some oftheir mobile devices' processing capability such as CPU, storage,network interfaces which then become part of the edge network. For thepurposes of this disclosure, owners of such mobile devices will bereferred to as “participants” and the mobile devices as “participatingdevices” or “participating mobile devices.” For such participatingdevices, there may be an application executing on the participatingdevices in a secure isolated container within the participating devices.The participant may configure a desired level of shared resources bydesignating, for example, power levels, CPU processing capability, orthe like, to be shared at various times or under various circumstances.Alternatively, there may be default configurations for the participatingmobile device.

Each participant may have their own usage profile for theirparticipating mobile devices. The participating mobile device and theusage profile may be registered to the nearest edge networking elementupon power-up and authenticated against a backend management server inthe network. Once enabled, the shared resources may be used forcomputation, storage, and/or routing traffic by the mobile devices ofother users of the network. For the purposes of this disclosure, suchusers of the network will be referred to as “users” and the mobiledevices as “user devices” or “user mobile devices.” It will beunderstood that it is possible for an individual to be both aparticipant and a user and for a mobile device to be both aparticipating mobile device and a user mobile device. When used alone,“mobile device” may refer to either a participating mobile device or auser mobile device.

The system may also include network applications executing on edgenetworking elements and connected to the participating mobile devices inthe coverage area that have opted to participate in the edge network.Based on the movement, direction, and speed of the connected user mobiledevices, the edge networking elements may alert adjacent edge networkingelements about the arriving user mobile device(s) to provide a seamlesshandoff of a user mobile device. As part of the handoff, the currentedge computing device communicating with the user mobile device may alsoprovide a copy of the authentication and last task being executed by theuser mobile device to the next edge networking element that willcommunicate with the user mobile device.

The edge networking element may manage the collective participant mobiledevice resources for servicing and transitioning user mobile devices toother edge networking elements or participating mobile devices. The edgenetworking element may logically separate the mobile application on eachparticipating mobile device to form isolated secure compartments toserve multiple tasks for different network users. The edge networkingelements may augment the separate containers to form a single logicalcomputation and communication unit for individual tasks. The secureisolated containers on individual participating devices are onlyaccessible to authorized entities and not even the host participatingmobile device may have such access.

In an aspect, users that are outside the coverage area of edge networkelements may still connect to the network by connecting to peer mobiledevices. Users that are outside the coverage area of both edge networkelements and other mobile devices may still connect to the backendsystem via the Internet or cellular network and then access an edgenetwork element. This and other functionality will be described ingreater detail below

Authentication of Network Devices. The disclosure provides a secure edgenetwork by integrating individual mobile devices to form a logical,dynamic, scalable and secure isolated network. Each mobile device may beauthenticated via a mobile device signature such as a public keymathematically related to hardware and software parameters of the devicethat form a private key. This private key may be referred to herein asthe mobile device DNA. The device DNA may be checked against a backendauthentication management server that contains the signatures (publickeys) upon initial registration. These are known as the permanent keys.Each network edge node, upon verifying and authenticating the mobiledevice, may create a temporary key pair for the life of a specific task.The temporary key may allow unrestricted access to containers working onthe same task.

It may be possible that the container be divided between multiple tasks.In that case, each task may be assigned a different temporary keyoperable on a single device.

Operating Environment. FIG. 1 shows an exemplary system 10 having usermobile devices 8 a, 8 b in communication with participating mobiledevice 12. Participating mobile device 12 is in communication with anedge network element 16. Participating mobile device 12 is alsodescribed in more detail with reference to FIG. 4 and FIG. 5 as UE 414and processor 500, respectively. The communication between participatingmobile device 12 and edge network element 16 may be through any wirelesscommunication network or method, including but not limited to cellular4G LTE and 5G networks. Each participating mobile device 12 may have anapplication 11 running thereon which allocates a portion of its localresources, including but not limited to, CPU processing, power, networkaccess through a network interface card, network bandwidth, storage,access to peripherals, or any other functionality on the participatingmobile device 12 to the network for extension of edge computingcapabilities. The allocation of each set of shared resources forindividual tasks may be isolated in one or more secure containers 13,14. While two secure containers 13, 14 are shown, it will be understoodthat the number of secure containers 13, 14 on each participating device12 may vary by location, network load, time of day, or resourcesrequired by participating devices for their own usage such as video orvoice calls or high bandwidth streaming or other heavy resource usageapplications. For example, secure container 13 may be allocated 10% ofthe CPU processing power of participating device 12 while securecontainer 14 may be allocated 15% of the CPU processing power of theparticipating device 12.

Continuing with the description of FIG. 1, there is also shown a networkedge element 15. The network edge element may be part of a largercommunication network having a core network 18 described in more detailherein. The network edge 15 may have radio access network (RAN)functionality configured to communicate with both participating mobiledevices 12 and user mobile devices 8 a, 8 b. With the network edgeelement 15, there is shown two individual task containers, 16, 17configured to communicate with secure containers 13, 14. Each networkedge element 15 may have an application 19 resident and running on thenetwork edge element 15.

Unlike traditional computing resources, network edge element 15 may beassigned or designated to work with data within a specific geographicarea. Network edge element 15 may be located in or near its assignedgeographic area. In an aspect, the network edge element 15 may beconfigured to communicate with both the participating mobile device 12and directly or indirectly to user mobile devices 8 a, 8 b in thegeographic area. While FIG. 1 shows one participating mobile device 12in communication with one network edge element 15, it will be understoodthat a single network edge element 15 may communicate with multipleparticipating mobile devices 12.

FIG. 1b shows an exemplary block functional diagram of an application 11running on participating mobile device 12. The application 11 may havean authentication module 21 to register on a backend management system36 through the network edge element 15 to enable the mobile device tobecome a participating mobile device 12. In an aspect, the network isexpanded as a secure edge network by integrating individualparticipating mobile devices 12 to form a logical, dynamic, scalable andsecure isolated network. Each participating mobile device 12 may beauthenticated via a participating mobile device 12 signature such as apublic key which is mathematically related to hardware and softwareparameters of the participating mobile device 12 that form a privatekey. This private key may be referred to herein as the participatingmobile device 12 DNA. The participating mobile device 12 DNA may bechecked against a backend authentication management server 36 thatcontains the signatures (public keys) associated with mobile devicesupon initial registration. These will be referred to as the “permanentkeys.”. Each network edge element 15, upon verifying and authenticatingthe participating mobile device 12, may create a temporary key pair forthe life of a specific task. The temporary key pair may allowunrestricted access to containers 13, 14 working on the same task. Itmay be possible that the container 13, 14 be divided between multipletasks. In that case, each task may be assigned a different temporary keyoperable on a single participating mobile device 12 and be authenticatedaccordingly.

Upon successful authentication, the shared resource module 21 mayreceive instructions to allocate resources on the participating mobiledevice 12 to use for one or more user mobile devices 8 a, 8 b. Theshared resource module 21 may allocate one or more resources to a usermobile device 8 a, 8 b to one or more task assigned by the network edgeelement 15. Included in the shared resources may be a slice of a networkinterface managed by the network interface module 23. A user mobiledevice 8 a, 8 b may communicate with the participating mobile device 12using a peer-to-peer communication link managed by peer-to-peerinterface module 22 and then communicate to the network edge elementthrough a network interface. The application 11 may also include aninternet protocol (IP) module 23 for communicating using IP protocol.

Operations. An exemplary operational architecture 30 is illustrated inFIG. 2a . There is shown two network edge elements 34 a, 34 b. As setforth previously, network edge elements 34 a, 34 b may be geographicallylocated to provide telecommunications and computer processing closer tothe areas where such services are needed. In this example, network edgeelements 34 a, 34 b are both located in region 1, while there are nonetwork edge elements located in regions 2 or 3.

There is also shown four participating mobile devices 32 a, 32 b, 32 c,32 d, all located in geographical region 1. All four participatingmobile devices 32 a, 32 b, 32 c, 32 d may be registered andauthenticated with backend management server 36. Participating mobiledevice 32 a is shown with one secure container 42 that is configured toprovide shared resources to a user mobile device. User mobile devicesare shown as 8 a, 8 b in FIG. 1, but are not shown in region 1 in FIG.3. It will be understood that the same or similar configuration existsfor any user mobile devices in region 1 in FIG. 3. The participatingmobile device 32 a is shown operating in conjunction with network edgeelement 34 a whereby secure container coded as “a” within participatingmobile device 32 a interacts with a corresponding container “a” onnetwork element 34 a. That link provides the ability for participatingmobile device 32 to share resources with a user mobile device 31 inRegion 2 for task “a” described below.

Continuing with the description in FIG. 2a , network edge element 34 bis shown interacting with 3 participating mobile devices 32 b, 32 c, 32b. There is shown task “b” which is shown connected to secure container“b” in participating mobile device 32 b and secure container “b” withinparticipating mobile device 32 c to provide services to a user mobiledevice in Region 1. If the user mobile device first interacts withparticipating mobile device 32 b and then by its speed and directionbegins to lose contact with participating mobile device 32 b, thennetwork edge element 34 b will coordinate a seamless handoff of the usermobile device to participating mobile device 32 c. User mobile deviceidentification, task and other relevant information may be passed toparticipating mobile device 32 c and upon successful transition, theshared resources of mobile device 32 b may be released. It will be notedthat in addition to a handoff from one participating mobile device toanother participating mobile device, there may be handoffs betweennetwork edge elements 34 a, 34 b.

There is also shown user mobile device 33 located in region 3 which inthis example is assumed to be outside the coverage area of the corenetwork 18 and network edge elements 34 a and 32 b. What otherwise wouldbe deemed to be in a “No Service Available” geographic area, user mobiledevice 33 may still be able to receive service through the expanded edgenetwork through participating mobile device 32 d. User mobile device 33may communicate with participating mobile device 32 d using peer-to-peercommunications and accessing secure container “c” to acquire sharedresources to connect to the network 18. Participating mobile device 32 dmay use its own resources or leverage the resources of network edgeelement 34 b and participating mobile device 32 c using securecontainers labeled “c”.

The system and method of the present disclosure may be extended toprovide network coverage internationally. For example, geographic zone 2may be located outside of the home country. Participating mobile device32 a may be used to provide shared resources to user mobile device 31.User mobile device 31 may connect to the backend management system 36via the Internet or roaming cellular network then to the network edgeelement 34 a and to participating mobile device 32 a through securecontainers labeled “a”. This allows a user mobile device 31 to useresources on its home network while traveling internationally, possiblyavoiding international roaming charges.

There is also shown a billing system interface 38. User mobile devices,for example, user mobile devices 31, 33 that desire or require theshared resources may be charged for the increased use of resources.Participating mobile devices 32 a, 32 b, 32 c, 32 d may obtain billingcredits for sharing of their resources or trade those resources forresources that they may need when the participating mobile devices 32 a,32 b, 32 c, 32 d are user mobile devices.

FIG. 2b is a flowchart for a method 200 for a participating mobiledevice 12. At 201, the participating mobile device registers with and isauthenticated with the backend management server 36. At 202, the networkedge element enables the participating mobile device to become an edgedevice. At 203, the participating mobile device makes its resourcesavailable to the network edge device. At 204, the user mobile device isconnected to the participating mobile device are used to provideservices to the user mobile device. The processing continues until 205when it is determined whether a hand-off of the user mobile device isrequired. If so, then at 206 it is determined whether anotherparticipating mobile device is available as a network interface toreceive the hand-off. If so, then the user device is connected to theparticipating mobile device back at 204 and the process repeats. Ifthere is no available participating mobile device, then the user deviceis handed off to the next available network interface resource at 207.

FIG. 2c shows an exemplary process 209 for connecting a user mobiledevice to a network when the user mobile device is outside of the normalnetwork coverage. At 210, the user mobile device registers with abackend management system though an interface such as, for example, theInternet or through a wireless network operated by another provider. At211, the backend management system establishes a connection with anetwork edge element. At 212, the network edge element establishes aconnection and defined tasks with a participating mobile device. At 213,the user device is operational on the network using resources madeavailable by the participating mobile device.

FIG. 2d shows an exemplary process 220 illustrating a method by which auser device 8 a may connect to the core network 18 through aparticipating mobile device 11. At 222, a peer-to-peer communicationlink is established between the user device 8 a and the participatingmobile device 11. At 223, the resources requested by the user mobiledevice 8 a are conveyed to the participating mobile device 11. At 224,the allocated resources are isolated in a secure container and accessedby the user mobile device 8 a. At 225, the user mobile device 8 aestablishes its connection to the core network through the sharedresources of participating mobile device 11.

In accordance with the above description, the system and method of thepresent disclosure provides a practical application that advances thestate of the telecommunications technology by creating a mechanism topush the edge of the network into individual participating mobiledevices within the edge network coverage area or remote from thatcoverage area. Moreover, the system and method of the present disclosureprovide the capability to securely and seamlessly integrate theseindividual participating mobile devices to form dynamic secure networkthat is not limited by geographical areas or what would otherwise beconstrained by such geographical areas.

In an exemplary operational feature, each user of a participating mobiledevice may contribute resources to the network and receive similarresources upon request from other participating mobile devices.Alternatively, a user mobile device may simply purchase the sharedresources as needed without allocating its own shared resources toothers.

Device and Network Description. FIG. 1 shows a box labeled core network18. What follows is an exemplary description of a core network 18. FIG.3 is a block diagram of network device 300 that may be connected to orcomprise a component of edge computing node 104 or connected to edgecomputing node 104 via a network. Network device 300 may comprisehardware or a combination of hardware and software. The functionality tofacilitate telecommunications via a telecommunications network mayreside in one or combination of network devices 300. Network device 300depicted in FIG. 3 may represent or perform functionality of anappropriate network device 300, or combination of network devices 300,such as, for example, a component or various components of a cellularbroadcast system wireless network, a processor, a server, a gateway, anode, a mobile switching center (MSC), a short message service center(SMSC), an ALFS, a gateway mobile location center (GMLC), a radio accessnetwork (RAN), a serving mobile location center (SMLC), or the like, orany appropriate combination thereof. It is emphasized that the blockdiagram depicted in FIG. 3 is exemplary and not intended to imply alimitation to a specific implementation or configuration. Thus, networkdevice 300 may be implemented in a single device or multiple devices(e.g., single server or multiple servers, single gateway or multiplegateways, single controller or multiple controllers). Multiple networkentities may be distributed or centrally located. Multiple networkentities may communicate wirelessly, via hard wire, or any appropriatecombination thereof.

Network device 300 may comprise a processor 302 and a memory 304 coupledto processor 302. Memory 304 may contain executable instructions that,when executed by processor 302, cause processor 302 to effectuateoperations associated with mapping wireless signal strength. As evidentfrom the description herein, network device 300 is not to be construedas software per se.

In addition to processor 302 and memory 304, network device 300 mayinclude an input/output system 306. Processor 302, memory 304, andinput/output system 306 may be coupled together (coupling not shown inFIG. 3) to allow communications therebetween. Each portion of networkdevice 300 may comprise circuitry for performing functions associatedwith each respective portion. Thus, each portion may comprise hardware,or a combination of hardware and software. Accordingly, each portion ofnetwork device 300 is not to be construed as software per se.Input/output system 306 may be capable of receiving or providinginformation from or to a communications device or other network entitiesconfigured for telecommunications. For example, input/output system 306may include a wireless communications (e.g., 3G/4G/GPS) card.Input/output system 306 may be capable of receiving or sending videoinformation, audio information, control information, image information,data, or any combination thereof. Input/output system 306 may be capableof transferring information with network device 300. In variousconfigurations, input/output system 306 may receive or provideinformation via any appropriate means, such as, for example, opticalmeans (e.g., infrared), electromagnetic means (e.g., RF, Wi-Fi,Bluetooth®, ZigBee®), acoustic means (e.g., speaker, microphone,ultrasonic receiver, ultrasonic transmitter), or a combination thereof.In an example configuration, input/output system 306 may comprise aWi-Fi finder, a two-way GPS chipset or equivalent, or the like, or acombination thereof.

Input/output system 306 of network device 300 also may contain acommunication connection 308 that allows network device 300 tocommunicate with other devices, network entities, or the like.Communication connection 308 may comprise communication media.Communication media typically embody computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism and includesany information delivery media. By way of example, and not limitation,communication media may include wired media such as a wired network ordirect-wired connection, or wireless media such as acoustic, RF,infrared, or other wireless media. The term computer-readable media asused herein includes both storage media and communication media.Input/output system 306 also may include an input device 310 such askeyboard, mouse, pen, voice input device, or touch input device.Input/output system 306 may also include an output device 312, such as adisplay, speakers, or a printer.

Processor 302 may be capable of performing functions associated withtelecommunications, such as functions for processing broadcast messages,as described herein. For example, processor 302 may be capable of, inconjunction with any other portion of network device 300, determining atype of broadcast message and acting according to the broadcast messagetype or content, as described herein.

Memory 304 of network device 300 may comprise a storage medium having aconcrete, tangible, physical structure. As is known, a signal does nothave a concrete, tangible, physical structure. Memory 304, as well asany computer-readable storage medium described herein, is not to beconstrued as a signal. Memory 304, as well as any computer-readablestorage medium described herein, is not to be construed as a transientsignal. Memory 304, as well as any computer-readable storage mediumdescribed herein, is not to be construed as a propagating signal. Memory304, as well as any computer-readable storage medium described herein,is to be construed as an article of manufacture.

Memory 304 may store any information utilized in conjunction withtelecommunications. Depending upon the exact configuration or type ofprocessor, memory 304 may include a volatile storage 314 (such as sometypes of RAM), a nonvolatile storage 316 (such as ROM, flash memory), ora combination thereof. Memory 304 may include additional storage (e.g.,a removable storage 318 or a nonremovable storage 320) including, forexample, tape, flash memory, smart cards, CD-ROM, DVD, or other opticalstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, USB-compatible memory, or any othermedium that can be used to store information and that can be accessed bynetwork device 300. Memory 304 may comprise executable instructionsthat, when executed by processor 302, cause processor 302 to effectuateoperations to map signal strengths in an area of interest.

FIG. 4 illustrates a functional block diagram depicting one example ofan LTE-EPS network architecture 400 related to the current disclosure.In particular, the network architecture 400 disclosed herein is referredto as a modified LTE-EPS architecture 400 to distinguish it from atraditional LTE-EPS architecture.

An example modified LTE-EPS architecture 400 is based at least in parton standards developed by the 3rd Generation Partnership Project (3GPP),with information available at www.3gpp.org. In one embodiment, theLTE-EPS network architecture 400 includes an access network 402, a corenetwork 404, e.g., an EPC or Common BackBone (CBB) and one or moreexternal networks 406, sometimes referred to as PDN or peer entities.Different external networks 406 can be distinguished from each other bya respective network identifier, e.g., a label according to DNS namingconventions describing an access point to the PDN. Such labels can bereferred to as Access Point Names (APN). External networks 406 caninclude one or more trusted and non-trusted external networks such as aninternet protocol (IP) network 408, an IP multimedia subsystem (IMS)network 410, and other networks 412, such as a service network, acorporate network, or the like.

Access network 402 can include an LTE network architecture sometimesreferred to as Evolved Universal Mobile Telecommunication SystemTerrestrial Radio Access (E UTRA) and evolved UMTS Terrestrial RadioAccess Network (E-UTRAN). Broadly, access network 402 can include one ormore communication devices, commonly referred to as UE 414, and one ormore wireless access nodes, or base stations 416 a, 416 b. Duringnetwork operations, at least one base station 416 communicates directlywith UE 414. Base station 416 can be an evolved Node B (e-NodeB), withwhich UE 414 communicates over the air and wirelessly. UEs 414 caninclude, without limitation, wireless devices, e.g., satellitecommunication systems, portable digital assistants (PDAs), laptopcomputers, tablet devices and other mobile devices (e.g., cellulartelephones, smart appliances, and so on). UEs 414 can connect to eNBs416 when UE 414 is within range according to a corresponding wirelesscommunication technology.

UE 414 generally runs one or more applications that engage in a transferof packets between UE 414 and one or more external networks 406. Suchpacket transfers can include one of downlink packet transfers fromexternal network 406 to UE 414, uplink packet transfers from UE 414 toexternal network 406 or combinations of uplink and downlink packettransfers. Applications can include, without limitation, web browsing,VoIP, streaming media and the like. Each application can pose differentQuality of Service (QoS) requirements on a respective packet transfer.Different packet transfers can be served by different bearers withincore network 404, e.g., according to parameters, such as the QoS.

Core network 404 uses a concept of bearers, e.g., EPS bearers, to routepackets, e.g., IP traffic, between a particular gateway in core network404 and UE 414. A bearer refers generally to an IP packet flow with adefined QoS between the particular gateway and UE 414. Access network402, e.g., E UTRAN, and core network 404 together set up and releasebearers as required by the various applications. Bearers can beclassified in at least two different categories: (i) minimum guaranteedbit rate bearers, e.g., for applications, such as VoIP; and (ii)non-guaranteed bit rate bearers that do not require guarantee bit rate,e.g., for applications, such as web browsing.

In one embodiment, the core network 404 includes various networkentities, such as MME 418, SGW 420, Home Subscriber Server (HSS) 422,Policy and Charging Rules Function (PCRF) 424 and PGW 426. In oneembodiment, MME 418 comprises a control node performing a controlsignaling between various equipment and devices in access network 402and core network 404. The protocols running between UE 414 and corenetwork 404 are generally known as Non-Access Stratum (NAS) protocols.

For illustration purposes only, the terms MME 418, SGW 420, HSS 422 andPGW 426, and so on, can be server devices, but may be referred to in thesubject disclosure without the word “server.” It is also understood thatany form of such servers can operate in a device, system, component, orother form of centralized or distributed hardware and software. It isfurther noted that these terms and other terms such as bearer pathsand/or interfaces are terms that can include features, methodologies,and/or fields that may be described in whole or in part by standardsbodies such as the 3GPP. It is further noted that some or allembodiments of the subject disclosure may in whole or in part modify,supplement, or otherwise supersede final or proposed standards publishedand promulgated by 3GPP.

According to traditional implementations of LTE-EPS architectures, SGW420 routes and forwards all user data packets. SGW 420 also acts as amobility anchor for user plane operation during handovers between basestations, e.g., during a handover from first eNB 416 a to second eNB 416b as may be the result of UE 414 moving from one area of coverage, e.g.,cell, to another. SGW 420 can also terminate a downlink data path, e.g.,from external network 406 to UE 414 in an idle state, and trigger apaging operation when downlink data arrives for UE 414. SGW 420 can alsobe configured to manage and store a context for UE 414, e.g., includingone or more of parameters of the IP bearer service and network internalrouting information. In addition, SGW 420 can perform administrativefunctions, e.g., in a visited network, such as collecting informationfor charging (e.g., the volume of data sent to or received from theuser), and/or replicate user traffic, e.g., to support a lawfulinterception. SGW 420 also serves as the mobility anchor forinterworking with other 3GPP technologies such as universal mobiletelecommunication system (UMTS).

At any given time, UE 414 is generally in one of three different states:detached, idle, or active. The detached state is typically a transitorystate in which UE 414 is powered on but is engaged in a process ofsearching and registering with network 402. In the active state, UE 414is registered with access network 402 and has established a wirelessconnection, e.g., radio resource control (RRC) connection, with eNB 416.Whether UE 414 is in an active state can depend on the state of a packetdata session, and whether there is an active packet data session. In theidle state, UE 414 is generally in a power conservation state in whichUE 414 typically does not communicate packets. When UE 414 is idle, SGW420 can terminate a downlink data path, e.g., from one peer entity 406,and triggers paging of UE 414 when data arrives for UE 414. If UE 414responds to the page, SGW 420 can forward the IP packet to eNB 416 a.

HSS 422 can manage subscription-related information for a user of UE414. For example, tHSS 422 can store information such as authorizationof the user, security requirements for the user, quality of service(QoS) requirements for the user, etc. HSS 422 can also hold informationabout external networks 406 to which the user can connect, e.g., in theform of an APN of external networks 406. For example, MME 418 cancommunicate with HSS 422 to determine if UE 414 is authorized toestablish a call, e.g., a voice over IP (VoIP) call before the call isestablished.

PCRF 424 can perform QoS management functions and policy control. PCRF424 is responsible for policy control decision-making, as well as forcontrolling the flow-based charging functionalities in a policy controlenforcement function (PCEF), which resides in PGW 426. PCRF 424 providesthe QoS authorization, e.g., QoS class identifier and bit rates thatdecide how a certain data flow will be treated in the PCEF and ensuresthat this is in accordance with the user's subscription profile.

PGW 426 can provide connectivity between the UE 414 and one or more ofthe external networks 406. In illustrative network architecture 400, PGW426 can be responsible for IP address allocation for UE 414, as well asone or more of QoS enforcement and flow-based charging, e.g., accordingto rules from the PCRF 424. PGW 426 is also typically responsible forfiltering downlink user IP packets into the different QoS-based bearers.In at least some embodiments, such filtering can be performed based ontraffic flow templates. PGW 426 can also perform QoS enforcement, e.g.,for guaranteed bit rate bearers. PGW 426 also serves as a mobilityanchor for interworking with non-3GPP technologies such as CDMA2000.

Within access network 402 and core network 404 there may be variousbearer paths/interfaces, e.g., represented by solid lines 428 and 430.Some of the bearer paths can be referred to by a specific label. Forexample, solid line 428 can be considered an S1-U bearer and solid line432 can be considered an S5/S8 bearer according to LTE-EPS architecturestandards. Without limitation, reference to various interfaces, such asS1, X2, S5, S8, S11 refer to EPS interfaces. In some instances, suchinterface designations are combined with a suffix, e.g., a “U” or a “C”to signify whether the interface relates to a “User plane” or a “Controlplane.” In addition, the core network 404 can include various signalingbearer paths/interfaces, e.g., control plane paths/interfacesrepresented by dashed lines 430, 434, 436, and 438. Some of thesignaling bearer paths may be referred to by a specific label. Forexample, dashed line 430 can be considered as an S1-MME signalingbearer, dashed line 434 can be considered as an S11 signaling bearer anddashed line 436 can be considered as an Sha signaling bearer, e.g.,according to LTE-EPS architecture standards. The above bearer paths andsignaling bearer paths are only illustrated as examples and it should benoted that additional bearer paths and signaling bearer paths may existthat are not illustrated.

Also shown is a novel user plane path/interface, referred to as theS1-U+ interface 466. In the illustrative example, the S1-U+ user planeinterface extends between the eNB 416 a and PGW 426. Notably, S1-U+path/interface does not include SGW 420, a node that is otherwiseinstrumental in configuring and/or managing packet forwarding betweeneNB 416 a and one or more external networks 406 by way of PGW 426. Asdisclosed herein, the S1-U+ path/interface facilitates autonomouslearning of peer transport layer addresses by one or more of the networknodes to facilitate a self-configuring of the packet forwarding path. Inparticular, such self-configuring can be accomplished during handoversin most scenarios so as to reduce any extra signaling load on the S/PGWs420, 426 due to excessive handover events.

In some embodiments, PGW 426 is coupled to storage device 440, shown inphantom. Storage device 440 can be integral to one of the network nodes,such as PGW 426, for example, in the form of internal memory and/or diskdrive. It is understood that storage device 440 can include registerssuitable for storing address values. Alternatively, or in addition,storage device 440 can be separate from PGW 426, for example, as anexternal hard drive, a flash drive, and/or network storage.

Storage device 440 selectively stores one or more values relevant to theforwarding of packet data. For example, storage device 440 can storeidentities and/or addresses of network entities, such as any of networknodes 418, 420, 422, 424, and 426, eNBs 416 and/or UE 414. In theillustrative example, storage device 440 includes a first storagelocation 442 and a second storage location 444. First storage location442 can be dedicated to storing a Currently Used Downlink address value442. Likewise, second storage location 444 can be dedicated to storing aDefault Downlink Forwarding address value 444. PGW 426 can read and/orwrite values into either of storage locations 442, 444, for example,managing Currently Used Downlink Forwarding address value 442 andDefault Downlink Forwarding address value 444 as disclosed herein.

In some embodiments, the Default Downlink Forwarding address for eachEPS bearer is the SGW S5-U address for each EPS Bearer. The CurrentlyUsed Downlink Forwarding address” for each EPS bearer in PGW 426 can beset every time when PGW 426 receives an uplink packet, e.g., a GTP-Uuplink packet, with a new source address for a corresponding EPS bearer.When UE 414 is in an idle state, the “Current Used Downlink Forwardingaddress” field for each EPS bearer of UE 414 can be set to a “null” orother suitable value.

In some embodiments, the Default Downlink Forwarding address is onlyupdated when PGW 426 receives a new SGW S5-U address in a predeterminedmessage or messages. For example, the Default Downlink Forwardingaddress is only updated when PGW 426 receives one of a Create SessionRequest, Modify Bearer Request and Create Bearer Response messages fromSGW 420.

As values 442, 444 can be maintained and otherwise manipulated on a perbearer basis, it is understood that the storage locations can take theform of tables, spreadsheets, lists, and/or other data structuresgenerally well understood and suitable for maintaining and/or otherwisemanipulate forwarding addresses on a per bearer basis.

It should be noted that access network 402 and core network 404 areillustrated in a simplified block diagram in FIG. 4. In other words,either or both of access network 402 and the core network 404 caninclude additional network elements that are not shown, such as variousrouters, switches and controllers. In addition, although FIG. 4illustrates only a single one of each of the various network elements,it should be noted that access network 402 and core network 404 caninclude any number of the various network elements. For example, corenetwork 404 can include a pool (i.e., more than one) of MMES 418, SGWs420 or PGWs 426.

In the illustrative example, data traversing a network path between UE414, eNB 416 a, SGW 420, PGW 426 and external network 406 may beconsidered to constitute data transferred according to an end-to-end IPservice. However, for the present disclosure, to properly performestablishment management in LTE-EPS network architecture 400, the corenetwork, data bearer portion of the end-to-end IP service is analyzed.

An establishment may be defined herein as a connection set up requestbetween any two elements within LTE-EPS network architecture 400. Theconnection set up request may be for user data or for signaling. Afailed establishment may be defined as a connection set up request thatwas unsuccessful. A successful establishment may be defined as aconnection set up request that was successful.

In one embodiment, a data bearer portion comprises a first portion(e.g., a data radio bearer 446) between UE 414 and eNB 416 a, a secondportion (e.g., an S1 data bearer 428) between eNB 416 a and SGW 420, anda third portion (e.g., an S5/S8 bearer 432) between SGW 420 and PGW 426.Various signaling bearer portions are also illustrated in FIG. 4. Forexample, a first signaling portion (e.g., a signaling radio bearer 448)between UE 414 and eNB 416 a, and a second signaling portion (e.g., S1signaling bearer 430) between eNB 416 a and MME 418.

In at least some embodiments, the data bearer can include tunneling,e.g., IP tunneling, by which data packets can be forwarded in anencapsulated manner, between tunnel endpoints. Tunnels, or tunnelconnections can be identified in one or more nodes of network 400, e.g.,by one or more of tunnel endpoint identifiers, an IP address and a userdatagram protocol port number. Within a particular tunnel connection,payloads, e.g., packet data, which may or may not include protocolrelated information, are forwarded between tunnel endpoints.

An example of first tunnel solution 450 includes a first tunnel 452 abetween two tunnel endpoints 454 a and 456 a, and a second tunnel 452 bbetween two tunnel endpoints 454 b and 456 b. In the illustrativeexample, first tunnel 452 a is established between eNB 416 a and SGW420. Accordingly, first tunnel 452 a includes a first tunnel endpoint454 a corresponding to an S1-U address of eNB 416 a (referred to hereinas the eNB S1-U address), and second tunnel endpoint 456 a correspondingto an S1-U address of SGW 420 (referred to herein as the SGW S1-Uaddress). Likewise, second tunnel 452 b includes first tunnel endpoint454 b corresponding to an S5-U address of SGW 420 (referred to herein asthe SGW S5-U address), and second tunnel endpoint 456 b corresponding toan S5-U address of PGW 426 (referred to herein as the PGW S5-U address).

In at least some embodiments, first tunnel solution 450 is referred toas a two tunnel solution, e.g., according to the GPRS Tunneling ProtocolUser Plane (GTPvl-U based), as described in 3GPP specification TS29.281, incorporated herein in its entirety. It is understood that oneor more tunnels are permitted between each set of tunnel end points. Forexample, each subscriber can have one or more tunnels, e.g., one foreach PDP context that they have active, as well as possibly havingseparate tunnels for specific connections with different quality ofservice requirements, and so on.

An example of second tunnel solution 458 includes a single or directtunnel 460 between tunnel endpoints 462 and 464. In the illustrativeexample, direct tunnel 460 is established between eNB 416 a and PGW 426,without subjecting packet transfers to processing related to SGW 420.Accordingly, direct tunnel 460 includes first tunnel endpoint 462corresponding to the eNB S1-U address, and second tunnel endpoint 464corresponding to the PGW S5-U address. Packet data received at eitherend can be encapsulated into a payload and directed to the correspondingaddress of the other end of the tunnel. Such direct tunneling avoidsprocessing, e.g., by SGW 420 that would otherwise relay packets betweenthe same two endpoints, e.g., according to a protocol, such as the GTP-Uprotocol.

In some scenarios, direct tunneling solution 458 can forward user planedata packets between eNB 416 a and PGW 426, by way of SGW 420. That is,SGW 420 can serve a relay function, by relaying packets between twotunnel endpoints 416 a, 426. In other scenarios, direct tunnelingsolution 458 can forward user data packets between eNB 416 a and PGW426, by way of the S1 U+ interface, thereby bypassing SGW 420.

Generally, UE 414 can have one or more bearers at any one time. Thenumber and types of bearers can depend on applications, defaultrequirements, and so on. It is understood that the techniques disclosedherein, including the configuration, management and use of varioustunnel solutions 450, 458, can be applied to the bearers on anindividual basis. That is, if user data packets of one bearer, say abearer associated with a VoIP service of UE 414, then the forwarding ofall packets of that bearer are handled in a similar manner. Continuingwith this example, the same UE 414 can have another bearer associatedwith it through the same eNB 416 a. This other bearer, for example, canbe associated with a relatively low rate data session forwarding userdata packets through core network 404 simultaneously with the firstbearer. Likewise, the user data packets of the other bearer are alsohandled in a similar manner, without necessarily following a forwardingpath or solution of the first bearer. Thus, one of the bearers may beforwarded through direct tunnel 458; whereas, another one of the bearersmay be forwarded through a two-tunnel solution 450.

FIG. 5 depicts an exemplary diagrammatic representation of a machine inthe form of a computer system 500 within which a set of instructions,when executed, may cause the machine to perform any one or more of themethods described above. One or more instances of the machine canoperate, for example, as processor 302, UE 414, eNB 416, MME 418, SGW420, HSS 422, PCRF 424, PGW 426 and other devices of FIGS. 1, 2, and 4.In some embodiments, the machine may be connected (e.g., using a network502) to other machines. In a networked deployment, the machine mayoperate in the capacity of a server or a client user machine in aserver-client user network environment, or as a peer machine in apeer-to-peer (or distributed) network environment.

The machine may comprise a server computer, a client user computer, apersonal computer (PC), a tablet, a smart phone, a laptop computer, adesktop computer, a control system, a network router, switch or bridge,or any machine capable of executing a set of instructions (sequential orotherwise) that specify actions to be taken by that machine. It will beunderstood that a communication device of the subject disclosureincludes broadly any electronic device that provides voice, video ordata communication. Further, while a single machine is illustrated, theterm “machine” shall also be taken to include any collection of machinesthat individually or jointly execute a set (or multiple sets) ofinstructions to perform any one or more of the methods discussed herein.

Computer system 500 may include a processor (or controller) 504 (e.g., acentral processing unit (CPU)), a graphics processing unit (GPU, orboth), a main memory 506 and a static memory 508, which communicate witheach other via a bus 510. The computer system 500 may further include adisplay unit 512 (e.g., a liquid crystal display (LCD), a flat panel, ora solid-state display). Computer system 500 may include an input device514 (e.g., a keyboard), a cursor control device 516 (e.g., a mouse), adisk drive unit 518, a signal generation device 520 (e.g., a speaker orremote control) and a network interface device 522. In distributedenvironments, the embodiments described in the subject disclosure can beadapted to utilize multiple display units 512 controlled by two or morecomputer systems 500. In this configuration, presentations described bythe subject disclosure may in part be shown in a first of display units512, while the remaining portion is presented in a second of displayunits 512.

The disk drive unit 518 may include a tangible computer-readable storagemedium 524 on which is stored one or more sets of instructions (e.g.,software 526) embodying any one or more of the methods or functionsdescribed herein, including those methods illustrated above.Instructions 526 may also reside, completely or at least partially,within main memory 506, static memory 508, or within processor 504during execution thereof by the computer system 500. Main memory 506 andprocessor 504 also may constitute tangible computer-readable storagemedia.

As shown in FIG. 6, telecommunication system 600 may include wirelesstransmit/receive units (WTRUs) 602, a RAN 604, a core network 606, apublic switched telephone network (PSTN) 608, the Internet 610, or othernetworks 612, though it will be appreciated that the disclosed examplescontemplate any number of WTRUs, base stations, networks, or networkelements. Each WTRU 602 may be any type of device configured to operateor communicate in a wireless environment. For example, a WTRU maycomprise drone 102, a mobile device, network device 300, or the like, orany combination thereof. By way of example, WTRUs 602 may be configuredto transmit or receive wireless signals and may include a UE, a mobilestation, a mobile device, a fixed or mobile subscriber unit, a pager, acellular telephone, a PDA, a smartphone, a laptop, a netbook, a personalcomputer, a wireless sensor, consumer electronics, or the like. WTRUs602 may be configured to transmit or receive wireless signals over anair interface 614.

Telecommunication system 600 may also include one or more base stations616. Each of base stations 616 may be any type of device configured towirelessly interface with at least one of the WTRUs 602 to facilitateaccess to one or more communication networks, such as core network 606,PTSN 608, Internet 610, or other networks 612. By way of example, basestations 616 may be a base transceiver station (BTS), a Node-B, an eNodeB, a Home Node B, a Home eNode B, a site controller, an access point(AP), a wireless router, or the like. While base stations 616 are eachdepicted as a single element, it will be appreciated that base stations616 may include any number of interconnected base stations or networkelements.

RAN 604 may include one or more base stations 616, along with othernetwork elements (not shown), such as a base station controller (BSC), aradio network controller (RNC), or relay nodes. One or more basestations 616 may be configured to transmit or receive wireless signalswithin a particular geographic region, which may be referred to as acell (not shown). The cell may further be divided into cell sectors. Forexample, the cell associated with base station 616 may be divided intothree sectors such that base station 616 may include three transceivers:one for each sector of the cell. In another example, base station 616may employ multiple-input multiple-output (MIMO) technology and,therefore, may utilize multiple transceivers for each sector of thecell.

Base stations 616 may communicate with one or more of WTRUs 602 over airinterface 614, which may be any suitable wireless communication link(e.g., RF, microwave, infrared (IR), ultraviolet (UV), or visiblelight). Air interface 614 may be established using any suitable radioaccess technology (RAT).

More specifically, as noted above, telecommunication system 600 may be amultiple access system and may employ one or more channel accessschemes, such as CDMA, TDMA, FDMA, OFDMA, SC-FDMA, or the like. Forexample, base station 616 in RAN 604 and WTRUs 602 connected to RAN 604may implement a radio technology such as Universal MobileTelecommunications System (UMTS) Terrestrial Radio Access (UTRA) thatmay establish air interface 614 using wideband CDMA (WCDMA). WCDMA mayinclude communication protocols, such as High-Speed Packet Access (HSPA)or Evolved HSPA (HSPA+). HSPA may include High-Speed Downlink PacketAccess (HSDPA) or High-Speed Uplink Packet Access (HSUPA).

As another example base station 616 and WTRUs 602 that are connected toRAN 604 may implement a radio technology such as Evolved UMTSTerrestrial Radio Access (E-UTRA), which may establish air interface 614using LTE or LTE-Advanced (LTE-A).

Optionally base station 616 and WTRUs 602 connected to RAN 604 mayimplement radio technologies such as IEEE 602.16 (i.e., WorldwideInteroperability for Microwave Access (WiMAX)), CDMA2000, CDMA2000 1×,CDMA2000 EV-DO, Interim Standard 2000 (IS-2000), Interim Standard 95(IS-95), Interim Standard 856 (IS-856), GSM, Enhanced Data rates for GSMEvolution (EDGE), GSM EDGE (GERAN), or the like.

Base station 616 may be a wireless router, Home Node B, Home eNode B, oraccess point, for example, and may utilize any suitable RAT forfacilitating wireless connectivity in a localized area, such as a placeof business, a home, a vehicle, a campus, or the like. For example, basestation 616 and associated WTRUs 602 may implement a radio technologysuch as IEEE 602.11 to establish a wireless local area network (WLAN).As another example, base station 616 and associated WTRUs 602 mayimplement a radio technology such as IEEE 602.15 to establish a wirelesspersonal area network (WPAN). In yet another example, base station 616and associated WTRUs 602 may utilize a cellular-based RAT (e.g., WCDMA,CDMA2000, GSM, LTE, LTE-A, etc.) to establish a picocell or femtocell.As shown in FIG. 6, base station 616 may have a direct connection toInternet 610. Thus, base station 616 may not be required to accessInternet 610 via core network 606.

RAN 604 may be in communication with core network 606, which may be anytype of network configured to provide voice, data, applications, and/orvoice over internet protocol (VoIP) services to one or more WTRUs 602.For example, core network 606 may provide call control, billingservices, mobile location-based services, pre-paid calling, Internetconnectivity, video distribution or high-level security functions, suchas user authentication. Although not shown in FIG. 6, it will beappreciated that RAN 604 or core network 606 may be in direct orindirect communication with other RANs that employ the same RAT as RAN604 or a different RAT. For example, in addition to being connected toRAN 604, which may be utilizing an E-UTRA radio technology, core network606 may also be in communication with another RAN (not shown) employinga GSM radio technology.

Core network 606 may also serve as a gateway for WTRUs 602 to accessPSTN 608, Internet 610, or other networks 612. PSTN 608 may includecircuit-switched telephone networks that provide plain old telephoneservice (POTS). For LTE core networks, core network 606 may use IMS core614 to provide access to PSTN 608. Internet 610 may include a globalsystem of interconnected computer networks or devices that use commoncommunication protocols, such as the transmission control protocol(TCP), user datagram protocol (UDP), or IP in the TCP/IP internetprotocol suite. Other networks 612 may include wired or wirelesscommunications networks owned or operated by other service providers.For example, other networks 612 may include another core networkconnected to one or more RANs, which may employ the same RAT as RAN 604or a different RAT.

Some or all WTRUs 602 in telecommunication system 600 may includemulti-mode capabilities. That is, WTRUs 602 may include multipletransceivers for communicating with different wireless networks overdifferent wireless links. For example, one or more WTRUs 602 may beconfigured to communicate with base station 616, which may employ acellular-based radio technology, and with base station 616, which mayemploy an IEEE 802 radio technology.

FIG. 7 is an example system 400 including RAN 604 and core network 606.As noted above, RAN 604 may employ an E-UTRA radio technology tocommunicate with WTRUs 602 over air interface 614. RAN 604 may also bein communication with core network 606.

RAN 604 may include any number of eNode-Bs 702 while remainingconsistent with the disclosed technology. One or more eNode-Bs 702 mayinclude one or more transceivers for communicating with the WTRUs 602over air interface 614. Optionally, eNode-Bs 702 may implement MIMOtechnology. Thus, one of eNode-Bs 702, for example, may use multipleantennas to transmit wireless signals to, or receive wireless signalsfrom, one of WTRUs 602.

Each of eNode-Bs 702 may be associated with a particular cell (notshown) and may be configured to handle radio resource managementdecisions, handover decisions, scheduling of users in the uplink ordownlink, or the like. As shown in FIG. 7 eNode-Bs 702 may communicatewith one another over an X2 interface.

Core network 606 shown in FIG. 7 may include a mobility managementgateway or entity (MME) 704, a serving gateway 706, or a packet datanetwork (PDN) gateway 708. While each of the foregoing elements aredepicted as part of core network 606, it will be appreciated that anyone of these elements may be owned or operated by an entity other thanthe core network operator.

MME 704 may be connected to each of eNode-Bs 702 in RAN 604 via an S1interface and may serve as a control node. For example, MME 704 may beresponsible for authenticating users of WTRUs 602, bearer activation ordeactivation, selecting a particular serving gateway during an initialattach of WTRUs 602, or the like. MME 704 may also provide a controlplane function for switching between RAN 604 and other RANs (not shown)that employ other radio technologies, such as GSM or WCDMA.

Serving gateway 706 may be connected to each of eNode-Bs 702 in RAN 604via the S1 interface. Serving gateway 706 may generally route or forwarduser data packets to or from the WTRUs 602. Serving gateway 706 may alsoperform other functions, such as anchoring user planes duringinter-eNode B handovers, triggering paging when downlink data isavailable for WTRUs 602, managing or storing contexts of WTRUs 602, orthe like.

Serving gateway 706 may also be connected to PDN gateway 708, which mayprovide WTRUs 602 with access to packet-switched networks, such asInternet 610, to facilitate communications between WTRUs 602 andIP-enabled devices.

Core network 606 may facilitate communications with other networks. Forexample, core network 606 may provide WTRUs 602 with access tocircuit-switched networks, such as PSTN 608, such as through IMS core614, to facilitate communications between WTRUs 602 and traditionalland-line communications devices. In addition, core network 606 mayprovide the WTRUs 602 with access to other networks 612, which mayinclude other wired or wireless networks that are owned or operated byother service providers.

FIG. 8 depicts an overall block diagram of an example packet-basedmobile cellular network environment, such as a GPRS network as describedherein. In the example packet-based mobile cellular network environmentshown in FIG. 8, there are a plurality of base station subsystems (BSS)800 (only one is shown), each of which comprises a base stationcontroller (BSC) 802 serving a plurality of BTSs, such as BTSs 804, 806,808. BTSs 804, 806, 808 are the access points where users ofpacket-based mobile devices become connected to the wireless network. Inexample fashion, the packet traffic originating from mobile devices istransported via an over-the-air interface to BTS 808, and from BTS 808to BSC 802. Base station subsystems, such as BSS 800, are a part ofinternal frame relay network 810 that can include a service GPRS supportnodes (SGSN), such as SGSN 812 or SGSN 814. Each SGSN 812, 814 isconnected to an internal packet network 816 through which SGSN 812, 814can route data packets to or from a plurality of gateway GPRS supportnodes (GGSN) 818, 820, 822. As illustrated, SGSN 814 and GGSNs 818, 820,822 are part of internal packet network 816. GGSNs 818, 820, 822 mainlyprovide an interface to external IP networks such as PLMN 824, corporateintranets/internets 826, or Fixed-End System (FES) or the publicInternet 828. As illustrated, subscriber corporate network 826 may beconnected to GGSN 820 via a firewall 830. PLMN 824 may be connected toGGSN 820 via a boarder gateway router (BGR) 832. A Remote AuthenticationDial-In User Service (RADIUS) server 834 may be used for callerauthentication when a user calls corporate network 826.

Generally, there may be a several cell sizes in a network, referred toas macro, micro, pico, femto or umbrella cells. The coverage area ofeach cell is different in different environments. Macro cells can beregarded as cells in which the base station antenna is installed in amast or a building above average roof top level. Micro cells are cellswhose antenna height is under average roof top level. Micro cells aretypically used in urban areas. Pico cells are small cells having adiameter of a few dozen meters. Pico cells are used mainly indoors.Femto cells have the same size as pico cells, but a smaller transportcapacity. Femto cells are used indoors, in residential or small businessenvironments. On the other hand, umbrella cells are used to covershadowed regions of smaller cells and fill in gaps in coverage betweenthose cells.

FIG. 9 illustrates an architecture of a typical GPRS network 900 asdescribed herein. The architecture depicted in FIG. 9 may be segmentedinto four groups: users 902, RAN 904, core network 906, and interconnectnetwork 908. Users 902 comprise a plurality of end users, who each mayuse one or more devices 910. Note that device 910 is referred to as amobile subscriber (MS) in the description of network shown in FIG. 9. Inan example, device 910 comprises a communications device (e.g., mobiledevice 102, mobile positioning center 116, network device 300, any ofdetected devices 500, second device 508, access device 604, accessdevice 606, access device 608, access device 610 or the like, or anycombination thereof). Radio access network 904 comprises a plurality ofBSSs such as BSS 912, which includes a BTS 914 and a BSC 916. Corenetwork 906 may include a host of various network elements. Asillustrated in FIG. 9, core network 906 may comprise MSC 918, servicecontrol point (SCP) 920, gateway MSC (GMSC) 922, SGSN 924, home locationregister (HLR) 926, authentication center (AuC) 928, domain name system(DNS) server 930, and GGSN 932. Interconnect network 908 may alsocomprise a host of various networks or other network elements. Asillustrated in FIG. 9, interconnect network 908 comprises a PSTN 934, anFES/Internet 936, a firewall 1038, or a corporate network 940.

An MSC can be connected to a large number of BSCs. At MSC 918, forinstance, depending on the type of traffic, the traffic may be separatedin that voice may be sent to PSTN 934 through GMSC 922, or data may besent to SGSN 924, which then sends the data traffic to GGSN 932 forfurther forwarding.

When MSC 918 receives call traffic, for example, from BSC 916, it sendsa query to a database hosted by SCP 920, which processes the request andissues a response to MSC 918 so that it may continue call processing asappropriate.

HLR 926 is a centralized database for users to register to the GPRSnetwork. HLR 926 stores static information about the subscribers such asthe International Mobile Subscriber Identity (IMSI), subscribedservices, or a key for authenticating the subscriber. HLR 926 alsostores dynamic subscriber information such as the current location ofthe MS. Associated with HLR 926 is AuC 928, which is a database thatcontains the algorithms for authenticating subscribers and includes theassociated keys for encryption to safeguard the user input forauthentication.

In the following, depending on context, “mobile subscriber” or “MS”sometimes refers to the end user and sometimes to the actual portabledevice, such as a mobile device, used by an end user of the mobilecellular service. When a mobile subscriber turns on his or her mobiledevice, the mobile device goes through an attach process by which themobile device attaches to an SGSN of the GPRS network. In FIG. 9, whenMS 910 initiates the attach process by turning on the networkcapabilities of the mobile device, an attach request is sent by MS 910to SGSN 924. The SGSN 924 queries another SGSN, to which MS 910 wasattached before, for the identity of MS 910. Upon receiving the identityof MS 910 from the other SGSN, SGSN 924 requests more information fromMS 910. This information is used to authenticate MS 910 together withthe information provided by HLR 926. Once verified, SGSN 924 sends alocation update to HLR 926 indicating the change of location to a newSGSN, in this case SGSN 924. HLR 926 notifies the old SGSN, to which MS910 was attached before, to cancel the location process for MS 910. HLR926 then notifies SGSN 924 that the location update has been performed.At this time, SGSN 924 sends an Attach Accept message to MS 910, whichin turn sends an Attach Complete message to SGSN 924.

Next, MS 910 establishes a user session with the destination network,corporate network 940, by going through a Packet Data Protocol (PDP)activation process. Briefly, in the process, MS 910 requests access tothe Access Point Name (APN), for example, UPS.com, and SGSN 924 receivesthe activation request from MS 910. SGSN 924 then initiates a DNS queryto learn which GGSN 932 has access to the UPS.com APN. The DNS query issent to a DNS server within core network 906, such as DNS server 930,which is provisioned to map to one or more GGSNs in core network 906.Based on the APN, the mapped GGSN 932 can access requested corporatenetwork 940. SGSN 924 then sends to GGSN 932 a Create PDP ContextRequest message that contains necessary information. GGSN 932 sends aCreate PDP Context Response message to SGSN 924, which then sends anActivate PDP Context Accept message to MS 910.

Once activated, data packets of the call made by MS 910 can then gothrough RAN 904, core network 906, and interconnect network 908, in aparticular FES/Internet 936 and firewall 1038, to reach corporatenetwork 940.

FIG. 10 illustrates a PLMN block diagram view of an example architecturethat may be replaced by a telecommunications system. In FIG. 10, solidlines may represent user traffic signals, and dashed lines may representsupport signaling. MS 1002 is the physical equipment used by the PLMNsubscriber. For example, drone 102, network device 300, the like, or anycombination thereof may serve as MS 1002. MS 1002 may be one of, but notlimited to, a cellular telephone, a cellular telephone in combinationwith another electronic device or any other wireless mobilecommunication device.

MS 1002 may communicate wirelessly with BSS 1004. BSS 1004 contains BSC1006 and a BTS 1008. BSS 1004 may include a single BSC 1006/BTS 1008pair (base station) or a system of BSC/BTS pairs that are part of alarger network. BSS 1004 is responsible for communicating with MS 1002and may support one or more cells. BSS 1004 is responsible for handlingcellular traffic and signaling between MS 1002 and a core network 1010.Typically, BSS 1004 performs functions that include, but are not limitedto, digital conversion of speech channels, allocation of channels tomobile devices, paging, or transmission/reception of cellular signals.

Additionally, MS 1002 may communicate wirelessly with RNS 1012. RNS 1012contains a Radio Network Controller (RNC) 1014 and one or more Nodes B1016. RNS 1012 may support one or more cells. RNS 1012 may also includeone or more RNC 1014/Node B 1016 pairs or alternatively a single RNC1014 may manage multiple Nodes B 1016. RNS 1012 is responsible forcommunicating with MS 1002 in its geographically defined area. RNC 1014is responsible for controlling Nodes B 1016 that are connected to it andis a control element in a UMTS radio access network. RNC 1014 performsfunctions such as, but not limited to, load control, packet scheduling,handover control, security functions, or controlling MS 1002 access tocore network 1010.

An E-UTRA Network (E-UTRAN) 1018 is a RAN that provides wireless datacommunications for MS 1002 and UE 1024. E-UTRAN 1018 provides higherdata rates than traditional UMTS. It is part of the LTE upgrade formobile networks, and later releases meet the requirements of theInternational Mobile Telecommunications (IMT) Advanced and are commonlyknown as a 4G networks. E-UTRAN 1018 may include of series of logicalnetwork components such as E-UTRAN Node B (eNB) 1020 and E-UTRAN Node B(eNB) 1022. E-UTRAN 1018 may contain one or more eNBs. User equipment(UE) 1024 may be any mobile device capable of connecting to E-UTRAN 1018including, but not limited to, a personal computer, laptop, mobiledevice, wireless router, or other device capable of wirelessconnectivity to E-UTRAN 1018. The improved performance of the E-UTRAN1018 relative to a typical UMTS network allows for increased bandwidth,spectral efficiency, and functionality including, but not limited to,voice, high-speed applications, large data transfer or IPTV, while stillallowing for full mobility.

Typically, MS 1002 may communicate with any or all of BSS 1004, RNS1012, or E-UTRAN 1018. In an illustrative system, each of BSS 1004, RNS1012, and E-UTRAN 1018 may provide MS 1002 with access to core network1010. Core network 1010 may include of a series of devices that routedata and communications between end users. Core network 1010 may providenetwork service functions to users in the circuit switched (CS) domainor the packet switched (PS) domain. The CS domain refers to connectionsin which dedicated network resources are allocated at the time ofconnection establishment and then released when the connection isterminated. The PS domain refers to communications and data transfersthat make use of autonomous groupings of bits called packets. Eachpacket may be routed, manipulated, processed or handled independently ofall other packets in the PS domain and does not require dedicatednetwork resources.

The circuit-switched MGW function (CS-MGW) 1026 is part of core network1010 and interacts with VLR/MSC server 1028 and GMSC server 1030 inorder to facilitate core network 1010 resource control in the CS domain.Functions of CS-MGW 1026 include, but are not limited to, mediaconversion, bearer control, payload processing or other mobile networkprocessing such as handover or anchoring. CS-MGW 1026 may receiveconnections to MS 1002 through BSS 1004 or RNS 1012.

SGSN 1032 stores subscriber data regarding MS 1002 in order tofacilitate network functionality. SGSN 1032 may store subscriptioninformation such as, but not limited to, the IMSI, temporary identities,or PDP addresses. SGSN 1032 may also store location information such as,but not limited to, GGSN address for each GGSN 1034 where an active PDPexists. GGSN 1034 may implement a location register function to storesubscriber data it receives from SGSN 1032 such as subscription orlocation information.

Serving gateway (S-GW) 1036 is an interface which provides connectivitybetween E-UTRAN 1018 and core network 1010. Functions of S-GW 1036include, but are not limited to, packet routing, packet forwarding,transport level packet processing, or user plane mobility anchoring forinter-network mobility. PCRF 1038 uses information gathered from P-GW1036, as well as other sources, to make applicable policy and chargingdecisions related to data flows, network resources or other networkadministration functions. PDN gateway (PDN-GW) 1040 may provideuser-to-services connectivity functionality including, but not limitedto, GPRS/EPC network anchoring, bearer session anchoring and control, orIP address allocation for PS domain connections.

HSS 1042 is a database for user information and stores subscription dataregarding MS 1002 or UE 1024 for handling calls or data sessions.Networks may contain one HSS 1042 or more if additional resources arerequired. Example data stored by HSS 1042 include, but is not limitedto, user identification, numbering or addressing information, securityinformation, or location information. HSS 1042 may also provide call orsession establishment procedures in both the PS and CS domains.

VLR/MSC Server 1028 provides user location functionality. When MS 1002enters a new network location, it begins a registration procedure. A MSCserver for that location transfers the location information to the VLRfor the area. A VLR and MSC server may be located in the same computingenvironment, as is shown by VLR/MSC server 1028, or alternatively may belocated in separate computing environments. A VLR may contain, but isnot limited to, user information such as the IMSI, the Temporary MobileStation Identity (TMSI), the Local Mobile Station Identity (LMSI), thelast known location of the mobile station, or the SGSN where the mobilestation was previously registered. The MSC server may containinformation such as, but not limited to, procedures for MS 1002registration or procedures for handover of MS 1002 to a differentsection of core network 1010. GMSC server 1030 may serve as a connectionto alternate GMSC servers for other MSs in larger networks.

EIR 1044 is a logical element which may store the IMEI for MS 1002. Userequipment may be classified as either “white listed” or “black listed”depending on its status in the network. If MS 1002 is stolen and put touse by an unauthorized user, it may be registered as “black listed” inEIR 1044, preventing its use on the network. A MME 1046 is a controlnode which may track MS 1002 or UE 1024 if the devices are idle.Additional functionality may include the ability of MME 1046 to contactidle MS 1002 or UE 1024 if retransmission of a previous session isrequired.

As described herein, a telecommunications system wherein management andcontrol utilizing a software designed network (SDN) and a simple IP arebased, at least in part, on user equipment, may provide a wirelessmanagement and control framework that enables common wireless managementand control, such as mobility management, radio resource management,QoS, load balancing, etc., across many wireless technologies, e.g. LTE,Wi-Fi, and future 5G access technologies; decoupling the mobilitycontrol from data planes to let them evolve and scale independently;reducing network state maintained in the network based on user equipmenttypes to reduce network cost and allow massive scale; shortening cycletime and improving network upgradability; flexibility in creatingend-to-end services based on types of user equipment and applications,thus improve customer experience; or improving user equipment powerefficiency and battery life—especially for simple M2M devices—throughenhanced wireless management.

While examples of a telecommunications system in which emergency alertscan be processed and managed have been described in connection withvarious computing devices/processors, the underlying concepts may beapplied to any computing device, processor, or system capable offacilitating a telecommunications system. The various techniquesdescribed herein may be implemented in connection with hardware orsoftware or, where appropriate, with a combination of both. Thus, themethods and devices may take the form of program code (i.e.,instructions) embodied in concrete, tangible, storage media having aconcrete, tangible, physical structure. Examples of tangible storagemedia include floppy diskettes, CD-ROMs, DVDs, hard drives, or any othertangible machine-readable storage medium (computer-readable storagemedium). Thus, a computer-readable storage medium is not a signal. Acomputer-readable storage medium is not a transient signal. Further, acomputer-readable storage medium is not a propagating signal. Acomputer-readable storage medium as described herein is an article ofmanufacture. When the program code is loaded into and executed by amachine, such as a computer, the machine becomes a device fortelecommunications. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile or nonvolatile memory or storage elements), at least one inputdevice, and at least one output device. The program(s) can beimplemented in assembly or machine language, if desired. The languagecan be a compiled or interpreted language and may be combined withhardware implementations.

The methods and devices associated with a telecommunications system asdescribed herein also may be practiced via communications embodied inthe form of program code that is transmitted over some transmissionmedium, such as over electrical wiring or cabling, through fiber optics,or via any other form of transmission, wherein, when the program code isreceived and loaded into and executed by a machine, such as an EPROM, agate array, a programmable logic device (PLD), a client computer, or thelike, the machine becomes an device for implementing telecommunicationsas described herein. When implemented on a general-purpose processor,the program code combines with the processor to provide a unique devicethat operates to invoke the functionality of a telecommunicationssystem.

While a telecommunications system has been described in connection withthe various examples of the various figures, it is to be understood thatother similar implementations may be used, or modifications andadditions may be made to the described examples of a telecommunicationssystem without deviating therefrom. For example, one skilled in the artwill recognize that a telecommunications system as described in theinstant application may apply to any environment, whether wired orwireless, and may be applied to any number of such devices connected viaa communications network and interacting across the network. Therefore,a telecommunications system as described herein should not be limited toany single example, but rather should be construed in breadth and scopein accordance with the appended claims.

The invention claimed is:
 1. A system comprising: a first participatingmobile device operating on a mobile network; a user device operating onthe mobile network; an input-output interface; a processing systemincluding a processor coupled to the input-output interface wherein theprocessing system is further coupled to a memory, the memory havingstored thereon executable instructions that when executed by theprocessing system cause the processing system to effectuate operationscomprising: identifying that the user device is outside a coverage areaof the mobile network; identifying that the first participating mobiledevice is within the coverage area of the mobile network; authenticatingthe first participating mobile device as an edge device on the mobilenetwork; allocating a first resource associated with a first service ofthe mobile network on the first participating mobile device to be usedfor serving the user device; receiving a request for the first servicefrom the user device; and causing the first participating mobile deviceto provide the first service to the user device using the firstresource.
 2. The system of claim 1, wherein the operations furthercomprise allocating a second resource associated with the first serviceon a second participating mobile device and causing the first service tobe transitioned from the first participating mobile device to the secondparticipating mobile device.
 3. The system of claim 2, wherein the firstparticipating mobile device provides an identification of a last taskbeing executed by the user device to the second participating mobiledevice.
 4. The system of claim 2, wherein the first participating mobiledevice and the second participating mobile device are in communicationwith a common network edge device.
 5. The system of claim 1, wherein theuser device connects to the mobile network through the firstparticipating mobile device.
 6. The system of claim 1, wherein the userdevice is authenticated on the mobile network.
 7. The system of claim 6,wherein the user device is authenticated on the mobile network through aregistration process on a backend server in the mobile network.
 8. Thesystem of claim 1, wherein a third resource is allocated on the firstparticipating mobile device and wherein the operations further comprisereceiving a request for a second service associated with the mobilenetwork from a second user device and causing the first participatingmobile device to provide the second service to the second user deviceusing the third resource.
 9. The system of claim 8, wherein the firstresource and the third resource are securely isolated from each other onthe first participating mobile device.
 10. The system of claim 1,wherein the first participating mobile device has a usage profilewherein the usage profile includes resources available to be allocatedas an edge device.
 11. The system of claim 1, wherein the first resourceis one of a computation, storage, or routing resource.
 12. A methodcomprising: registering, by a mobile device including a processor, as aparticipating mobile device on a mobile network, wherein the mobiledevice is within a coverage area of the mobile network; authenticatingthe participating mobile device as an edge device through a back-endserver on the mobile network; allocating, by the mobile device, aportion of available resources to be shared with a user device, whereinthe user device is outside the coverage area of the mobile network;establishing, by the mobile device, a first communication with the userdevice using the portion of available resources; and providing, by themobile device, a first service to the user device using the portion ofavailable resources of the participating mobile device.
 13. The methodof claim 12, further comprising handing off, by the mobile device, thefirst communication to one of an edge network device or a secondparticipating device.
 14. The method of claim 12, further comprisingallocating, by the mobile device, a second portion of availableresources to be shared with a second user device and establishing asecond communication with the second user device.
 15. The method ofclaim 12, further comprising establishing, by the mobile device, asecond communication with an edge network device and wherein the userdevice is authenticated through the back-end server and the firstcommunication is initiated by the edge network device.
 16. The method ofclaim 12, wherein the establishing of the first communication isinitiated by the user device.
 17. The method of claim 12, furthercomprising receiving billing credits for sharing resources used in thefirst communication.
 18. A mobile device comprising: a processing systemincluding a processor; a user device portion configured to operate on amobile network; a participating mobile device portion configured tooperate as an edge device on the mobile network wherein theparticipating mobile device portion and the user device portion areisolated from each other in secure containers; an application configuredto execute on the mobile device, the application having storedexecutable instructions in a memory that when executed by the processingsystem cause the processing system to effectuate operations comprising:identifying that a second user device is outside a coverage area of themobile network; identifying that the mobile device is within thecoverage area of the mobile network; registering on the mobile networkas a participating mobile device; receiving a first communication from afirst edge device on the mobile network, the first communicationcontaining a request for resources to be used by the second user device;and establishing a second communication with the second user device. 19.The mobile device of claim 18 wherein the second communication includesproviding operating resources from the participating mobile deviceportion to be used by the second user device.
 20. The mobile device ofclaim 18 wherein the participating mobile device portion is divided intotwo secure containers, each of the secure containers having resources tobe allocated to the second user device and a third user device.